Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

datastore::switch_epochとlog_channel::begin_sessionの呼出しがオーバラップする可能性についてapi コメントに追記 #54

Merged
merged 2 commits into from
Sep 24, 2024

Conversation

kuron99
Copy link
Contributor

@kuron99 kuron99 commented Sep 24, 2024

会議で議論した内容 ( https://github.com/project-tsurugi/tsurugi-issues/issues/925 )に従ってlimestone API doc commentに追記したいと思います。

@umegane レビューのうえ、問題なければマージお願いします。

@umegane
Copy link
Contributor

umegane commented Sep 24, 2024

@kuron99

datastore::switch_epoch() and this function can be called simultaneously.

この部分はOK

If these functions invocation overwrap, the current epoch that the session joins depends on timing.

この部分は、

  • 具体的にどのような値を取るのか不明確
  • 必ずしもタイミング依存ではないかもしれない

という点が気になります。次のようなコメントが良いと思うのですが、いかがでしょうか。

datastore::switch_epoch() and this function can be called simultaneously. If these functions are invoked at the same time, the result will be as if one of them was called first, but it is indeterminate which one will take precedence.

@kuron99
Copy link
Contributor Author

kuron99 commented Sep 24, 2024

なるほど、「関数呼び出し同士に前後はつくがどちらが先になるかは不定」という書き方ですね。よさそうに思います。この内容でブランチを更新しました。

@umegane umegane merged commit 4b8e230 into master Sep 24, 2024
6 checks passed
@umegane
Copy link
Contributor

umegane commented Sep 24, 2024

問題ないと思うのでマージしました。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants